-
Notifications
You must be signed in to change notification settings - Fork 3.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs: Update named edx-platform maintainers. #34746
Conversation
Currently this group contains @feanil and @kdmccormick though more maintainers can be added in the future. While 2u-arch-bom has done a great job thus far maintaining this repo, they don't currently have the capacity to help drive maintenance of edx-platform moving forward. This update should help make it easier to get help and coordinate work on edx-platform moving forward.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me, presuming we keep this open for a week for others' comments.
Feanil, I think one of our first jobs now that Redwood is cut is to figure out a way to distribute maintenance of various areas of edx-platform. I imagine that issues will be surfacing soon from Redwood testing, which will give us a good first test of any new system. Let's start that at next week's meeting.
In the immediate term, I can also personally commit to continuing to drive deprecations like Paver and Blockstore, kicking off the process of revising or replacing OEP-45 for edx-platform, pushing forward the migration to Learning Core, reviewing cross-cutting edx-platform PRs, and generally keeping an eye on the edx-platform issue log and finding volunteers to help keep the platform moving forward in various ways. For anyone curious, here's a longer-term vision I have for improvements.
As to who should be on this team--I'm open to with any experienced contributor who is willing to make specific commitments to help Feanil and I lead edx-platform maintenance.
@feanil given the examples you provided above where 2U was also vital to the effort, the discussions that have happened around shared maintenance, 2U involvement in the Maintenance WG, and the dedicated resources that 2U eng has supplied for edx-platform maintenance... would it make sense to you to also have either myself or @robrap as an additional member of the maintenance wg team? |
In addition to @jristau1984's other points, and to avoid having a single person from our earlier group, and given that we both continue to join all maintenance meetings, I'd prefer that @robrap (that's me) and @jristau1984 both get added. |
@jristau1984 @robrap thanks for the feedback, I've added you to the team being updated here. |
Thanks so much. We greatly appreciate the consideration, @feanil ! |
2U Release Notice: This PR has been deployed to the edX staging environment in preparation for a release to production. |
2U Release Notice: This PR has been deployed to the edX production environment. |
Currently this group contains @feanil and @kdmccormick though more
maintainers can be added in the future. While 2u-arch-bom has done a
great job thus far maintaining this repo, they don't currently have the
capacity to help drive maintenance of edx-platform moving forward.
This update should help make it easier to get help and coordinate work
on edx-platform moving forward.
It's not currently documented how one joins this group but I think some reasonable expectations of anyone who is interested is that they need to make a specific committment to leading maintenance of edx-platform. In the cases of Kyle and myself, using the recent Python 3.11 Upgrade, Node 18, and Paver Deprecation work as examples, we're comitted to spending time both doing the work of keeping edx-platform up to date and cleaning up cruft and complexities that make it harder to work with.